Closed
Bug 1622655
Opened 5 years ago
Closed 5 years ago
the 'empty' method should be used to check for emptiness instead of 'size'
Categories
(Developer Infrastructure :: Source Code Analysis, task)
Developer Infrastructure
Source Code Analysis
Tracking
(firefox77 fixed)
RESOLVED
FIXED
mozilla77
| Tracking | Status | |
|---|---|---|
| firefox77 | --- | fixed |
People
(Reporter: Sylvestre, Assigned: joshuagahan, Mentored)
References
(Blocks 1 open bug)
Details
(Keywords: good-first-bug, Whiteboard: [lang=C++])
Attachments
(1 file)
+++ This bug was initially created as a clone of Bug #1622653 +++
Filling as a good first bug to learn workflows.
!mInvalidationListeners.size()
should use .empty() instead
https://searchfox.org/mozilla-central/source/gfx/2d/FilterNodeSoftware.cpp#907
As the change is trivial, it is just to learn how to contribute to Firefox.
Found by http://clang.llvm.org/extra/clang-tidy/checks/readability-container-size-empty.html
Tutorial to contribute:
https://firefox-source-docs.mozilla.org/tools/docs/contribute/how_to_contribute_firefox.html
Please don't ask for the bug to be assigned. It will be automatically assigned to the first patch.
|
Reporter | |
Updated•5 years ago
|
|
Assignee | |
Comment 1•5 years ago
|
||
|
||
Updated•5 years ago
|
Assignee: nobody → joshuagahan
Status: NEW → ASSIGNED
|
|
||
Updated•5 years ago
|
Attachment #9139649 -
Attachment description: Bug 1622655 - Replaced !mInvalidationListeners.size() with .empty(). r?sylvestre → Bug 1622655 - Replaced !mInvalidationListeners.size() with mInvalidationListeners.empty(). r?sylvestre
Pushed by sledru@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/d31fb819d4a0
Replaced !mInvalidationListeners.size() with mInvalidationListeners.empty(). r=sylvestre
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox77:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla77
|
||
Updated•3 years ago
|
Product: Firefox Build System → Developer Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•